Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

chore(deps): update dependency webpack to v5.90.3 #13133

Merged
merged 1 commit into from
Mar 18, 2024
Merged

chore(deps): update dependency webpack to v5.90.3 #13133

merged 1 commit into from
Mar 18, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 30, 2024 •
edited
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
webpack 5.89.0 -> 5.90.3 age adoption passing confidence

Release Notes

webpack/webpack (webpack)

v5.90.3

Compare Source

Bug Fixes

  • don't mangle when destructuring a reexport
  • types for Stats.toJson() and Stats.toString()
  • many internal types
  • [CSS] clean up export css local vars

Perf

  • simplify and optimize chunk graph creation

v5.90.2

Compare Source

Bug Fixes

  • use Math.imul in fnv1a32 to avoid loss of precision, directly hash UTF16 values
  • the setStatus() of the HMR module should not return an array, which may cause infinite recursion
  • __webpack_exports_info__.xxx.canMangle shouldn't always same as default
  • mangle export with destructuring
  • use new runtime to reconsider skipped connections activeState
  • make dynamic import optional in try/catch
  • improve auto publicPath detection

Dependencies & Maintenance

  • improve CI setup and include Node.js@21

v5.90.1

Compare Source

Bug Fixes

  • set unmanagedPaths in defaults
  • correct preOrderIndex and postOrderIndex
  • add fallback for MIME mismatch error in async wasm loading
  • browsers versions of ECMA features

Performance

  • optimize compareStringsNumeric
  • optimize numberHash using 32-bit FNV1a for small ranges, 64-bit for larger
  • reuse VM context across webpack magic comments

v5.90.0

Compare Source

Bug Fixes

  • Fixed inner graph for classes
  • Optimized RemoveParentModulesPlugin via bigint arithmetic
  • Fixed worklet detection in production mode
  • Fixed an error for cyclic importModule
  • Fixed types for Server and Dirent
  • Added the fetchPriority to hmr runtime's ensureChunk function
  • Don't warn about dynamic import for build dependencies
  • External module generation respects the output.environment.arrowFunction option
  • Fixed consumimng shared runtime module logic
  • Fixed a runtime logic of multiple chunks
  • Fixed destructing assignment of dynamic import json file
  • Passing errors array for a module hash
  • Added /*#__PURE__*/ to generated JSON.parse()
  • Generated a library manifest after clean plugin
  • Fixed non amd externals and amd library
  • Fixed a bug in SideEffectsFlagPlugin with namespace re-exports
  • Fixed an error message for condition or
  • The strictModuleErrorHandling is now working
  • Clean up child compilation chunk graph to avoid memory leak
  • [CSS] - Fixed CSS import prefer relative resolution
  • [CSS] - Fixed CSS runtime chunk loading error message

New Features

  • Allow to set false for dev server in webpack.config.js
  • Added a warning for async external when not supported
  • Added a warning for async module when not supported
  • Added the node-module option for the node.__filename/__dirname and enable it by default for ESM target
  • Added the snapshot.unmanagedPaths option
  • Exposed the MultiCompilerOptions type
  • [CSS] - Added CSS parser options to enable/disable named exports
  • [CSS] - Moved CSS the exportsOnly option to CSS generator options

Dependencies & Maintenance

  • use node.js LTS version for lint
  • bump actions/cache from 3 to 4
  • bump prettier from 3.2.1 to 3.2.3
  • bump assemblyscript
  • bump actions/checkout from 3 to 4

Full Changelog: webpack/webpack@v5.89.0...v5.90.0

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Jan 30, 2024
@renovate Renovate
Copy link
Contributor Author

renovate bot commented Jan 30, 2024 •
edited
Loading

⚠ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: sample/31-graphql-federation-code-first/users-application/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/graphql@12.0.11
npm ERR! Found: reflect-metadata@0.2.1
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/common@10.3.2
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"10.3.2" from the root project
npm ERR!     peer @nestjs/common@"^9.3.8 || ^10.0.0" from @nestjs/apollo@12.0.11
npm ERR!     node_modules/@nestjs/apollo
npm ERR!       @nestjs/apollo@"12.0.11" from the root project
npm ERR!     5 more (@nestjs/core, @nestjs/graphql, @nestjs/mapped-types, ...)
npm ERR!   1 more (@nestjs/core)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/graphql@12.0.11
npm ERR! node_modules/@nestjs/graphql
npm ERR!   @nestjs/graphql@"12.0.11" from the root project
npm ERR!   peer @nestjs/graphql@"^12.0.0" from @nestjs/apollo@12.0.11
npm ERR!   node_modules/@nestjs/apollo
npm ERR!     @nestjs/apollo@"12.0.11" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: reflect-metadata@0.1.14
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/graphql@12.0.11
npm ERR!   node_modules/@nestjs/graphql
npm ERR!     @nestjs/graphql@"12.0.11" from the root project
npm ERR!     peer @nestjs/graphql@"^12.0.0" from @nestjs/apollo@12.0.11
npm ERR!     node_modules/@nestjs/apollo
npm ERR!       @nestjs/apollo@"12.0.11" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-18T08_51_56_925Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-18T08_51_56_925Z-debug-0.log
File name: sample/31-graphql-federation-code-first/gateway/package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/graphql@12.0.11
npm ERR! Found: reflect-metadata@0.2.1
npm ERR! node_modules/reflect-metadata
npm ERR!   reflect-metadata@"0.2.1" from the root project
npm ERR!   peer reflect-metadata@"^0.1.12 || ^0.2.0" from @nestjs/common@10.3.2
npm ERR!   node_modules/@nestjs/common
npm ERR!     @nestjs/common@"10.3.2" from the root project
npm ERR!     peer @nestjs/common@"^9.3.8 || ^10.0.0" from @nestjs/apollo@12.0.11
npm ERR!     node_modules/@nestjs/apollo
npm ERR!       @nestjs/apollo@"12.0.11" from the root project
npm ERR!     5 more (@nestjs/core, @nestjs/graphql, @nestjs/mapped-types, ...)
npm ERR!   1 more (@nestjs/core)
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer reflect-metadata@"^0.1.13" from @nestjs/graphql@12.0.11
npm ERR! node_modules/@nestjs/graphql
npm ERR!   @nestjs/graphql@"12.0.11" from the root project
npm ERR!   peer @nestjs/graphql@"^12.0.0" from @nestjs/apollo@12.0.11
npm ERR!   node_modules/@nestjs/apollo
npm ERR!     @nestjs/apollo@"12.0.11" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: reflect-metadata@0.1.14
npm ERR! node_modules/reflect-metadata
npm ERR!   peer reflect-metadata@"^0.1.13" from @nestjs/graphql@12.0.11
npm ERR!   node_modules/@nestjs/graphql
npm ERR!     @nestjs/graphql@"12.0.11" from the root project
npm ERR!     peer @nestjs/graphql@"^12.0.0" from @nestjs/apollo@12.0.11
npm ERR!     node_modules/@nestjs/apollo
npm ERR!       @nestjs/apollo@"12.0.11" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2024-03-18T08_52_04_432Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-03-18T08_52_04_432Z-debug-0.log

@coveralls
Copy link

coveralls commented Jan 30, 2024 •
edited
Loading

Pull Request Test Coverage Report for Build 6bd09931-b168-4df2-9bfd-aa51c51d4f1d

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 92.18%
Totals Coverage Status
Change from base Build 1e0356a2-e22d-4b55-94de-8e14e827e7c7: 0.0%
Covered Lines: 6731
Relevant Lines: 7302
💛 - Coveralls

@renovate renovate bot force-pushed the renovate/webpack-5.x branch 4 times, most recently from 9116b1e to 27f7b8c Compare February 1, 2024 20:22
@renovate renovate bot changed the title chore(deps): update dependency webpack to v5.90.0 chore(deps): update dependency webpack to v5.90.1 Feb 1, 2024
@renovate renovate bot force-pushed the renovate/webpack-5.x branch 10 times, most recently from 52699e9 to c3a516c Compare February 7, 2024 12:07
@renovate renovate bot force-pushed the renovate/webpack-5.x branch 7 times, most recently from 3cb9fdd to e02cb7f Compare February 15, 2024 16:20
@renovate renovate bot changed the title chore(deps): update dependency webpack to v5.90.1 chore(deps): update dependency webpack to v5.90.2 Feb 15, 2024
@renovate renovate bot force-pushed the renovate/webpack-5.x branch 2 times, most recently from 056138c to 2ef8023 Compare February 19, 2024 13:09
@renovate renovate bot changed the title chore(deps): update dependency webpack to v5.90.2 chore(deps): update dependency webpack to v5.90.3 Feb 19, 2024
@abjerry97 abjerry97 mentioned this pull request Jun 12, 2024
Open
@dagistan-tuncbilek dagistan-tuncbilek mentioned this pull request Jun 14, 2024
Open
@Cabreira97 Cabreira97 mentioned this pull request Jun 18, 2024
Merged
This was referenced Jun 21, 2024
Open
Open
@ai-leonid ai-leonid mentioned this pull request Jun 25, 2024
Open
@Cabreira97 Cabreira97 mentioned this pull request Jun 25, 2024
Merged
This was referenced Jun 29, 2024
Closed
Merged
Merged
Merged
@origranot origranot mentioned this pull request Jul 17, 2024
Merged
This was referenced Aug 21, 2024
Open
Open
Open
@ambrose40 ambrose40 mentioned this pull request Aug 29, 2024
Open
This was referenced Sep 4, 2024
Open
Open
Open
@unaise97 unaise97 mentioned this pull request Sep 5, 2024
Open
@tajul-saajan tajul-saajan mentioned this pull request Sep 7, 2024
Open
@carlotiii30 carlotiii30 mentioned this pull request Sep 8, 2024
Open
This was referenced Sep 13, 2024
Open
Open
@ilovepixelart ilovepixelart mentioned this pull request Sep 15, 2024
Open
@XavierMP14 XavierMP14 mentioned this pull request Sep 17, 2024
Open
@ilovepixelart ilovepixelart mentioned this pull request Sep 18, 2024
Open
@mauriciocarvalho01 mauriciocarvalho01 mentioned this pull request Sep 19, 2024
Open
@ilovepixelart ilovepixelart mentioned this pull request Sep 19, 2024
Open
@m0hs1ne m0hs1ne mentioned this pull request Sep 21, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@coveralls @kamilmysliwiec